Release tracking#7907
Open
primer[bot] wants to merge 1 commit into
Open
Conversation
Contributor
❗ Pre-merge checklistPlease ensure these items are checked before merging: 🔎 Smoke test
🌏 Integration tests
✅ Peer Review
🤔 Sanity test
❗ Post-merge checklistPlease ensure these items are checked after merging: 🚢 Version upgrade, cleanup, and documentation
|
Contributor
|
6a367a5 to
82d74c5
Compare
82d74c5 to
972c04f
Compare
972c04f to
179829f
Compare
179829f to
bfb2839
Compare
bfb2839 to
1c9d7ea
Compare
1c9d7ea to
89aa3e9
Compare
89aa3e9 to
040f4cc
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@primer/react@38.27.0
Minor Changes
#7900
49a546fThanks @mattcosta7! -PageLayout.Sidebar(andSplitPageLayout.Sidebar): add controlled-width support viacurrentWidth+onResizeEnd, matching the discriminated-union API already onPageLayout.Pane. The underlyingusePaneWidthhook already supported these options; this wires them through the component's prop surface. Existing usage is unchanged — the props are opt-in and the uncontrolled (default orwidthStorageKey-backed) behavior is preserved exactly.#7906
adc5299Thanks @jonrohan! - Text: AddwhiteSpaceprop to control the CSSwhite-spacepropertyPatch Changes
#7915
f58e448Thanks @jonrohan! - Dialog: FixEscapekey not closing the dialog on the first keypress when the close button is focused#7908
e9a2254Thanks @jonrohan! -KeybindingHint: display theMetakey correctly on platforms other than macOS and Windows. TheMeta,Alt, andModkeys are now resolved based on the detected platform: Apple platforms (macOS and iOS) show⌘/⌥, Windows showsWin, and all other platforms showMeta/Alt.#7894
af4541dThanks @mattcosta7! - ActionList: Replace:has(...)selectors onActionList.Item,InactiveButtonWrap, andTrailingActionButtonwith JS-derived data attributes (data-has-trailing-action,data-trailing-action-loading,data-position,data-has-label). Reduces style-recalculation cost on lists that render many items. No visual or behavioral changes.#7899
9659ce7Thanks @mattcosta7! -TreeView: make rows safer to use withcontain: paint/content-visibility: autoand reduce style-recalc cost on hover/focus in large trees. No visual or layout changes; all changes are either invisible at the default rendering or behind an opt-in CSS containment property the consumer sets.left: -8pxof the row container) was being clipped when a consumer appliedcontain: paintto the<li>or when the documentedcontainIntrinsicSizeprop onTreeView.Itemtriggeredcontent-visibility: autoon the row container — including forcurrentitems. Both.TreeViewItemand.TreeViewItemContainernow declareoverflow-clip-margin: var(--base-size-8), which extends the paint-clip edge by 8px on the side the indicator paints. The property is a no-op when no paint containment is active, so default rendering is byte-identical.:has(.TreeViewItemSkeleton), which forced subtree invalidation on every row.LoadingItemnow communicates with the placeholderItemvia a module-private context that emits a positivedata-loadingattribute on the<li>, and the CSS selector targets that directly. No new public prop.:hover/:focus-withindescendant selector. Color is driven by an inherited--tree-line-colorcustom property set on the root<ul>, so a hover or focus change inside the tree updates one property on one element instead of re-matching.TreeViewItemLevelLineselectors against every level line in the tree.outline-offset: -2in the forced-colors focus-ring fallback that browsers were silently dropping (so forced-colors users now actually get a focus indicator on tree items)..TreeViewItemContainer'sgrid-template-columnsnow declares thetrailingActioncolumn explicitly (auto) so it matches the 5-areagrid-template-areasdeclaration (previously the trailing column was implicitauto).